Enhancement to system information block (SIB) validity check for non-public networks (NPNs)

ABSTRACT

This disclosure provides systems, methods, and apparatus, including computer programs encoded on computer storage media, for operating a user equipment (UE) in a next generation (NG) radio access network (RAN) (NG-RAN) to validate a system information block (SIB) for non-public networks (NPNs). In one aspect, a UE receiving a SIB-one (SIB1) from a cell of the NG-RAN may determine whether the cell supports non-public networks (NPNs) based on the received SIB1. If so case, the UE may determine whether an NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-ID of a SIB stored in memory. If so, the UE may validate the stored SIB based at least in part on the received SIB1. If not, the UE may invalidate the stored SIB and obtain a new SIB per standard procedures.

RELATED APPLICATIONS

This application claims the benefit of priority to U.S. ProvisionalApplication No. 62/936,912 entitled “ENHANCEMENT TO SYSTEM INFORMATIONBLOCK (SIB) VALIDITY CHECK FOR NON-PUBLIC NETWORKS (NPNs)” filed Nov.18, 2019, the entire contents of which are hereby incorporated byreference for all purposes.

TECHNICAL FIELD

This disclosure relates to operations using system information blocks(SIBs) in next generation (NG) radio access networks (RANs) (NG-RANs).

DESCRIPTION OF THE RELATED TECHNOLOGY

Long Term Evolution (LTE), Fifth Generation (5G)—new radio (NR), andother recently developed communication technologies allow wirelessdevices to communicate information at data rates (such as in terms ofGigabits per second, etc.) that are orders of magnitude greater thanwhat was available just a few years ago.

Today's communication networks are also more secure, resilient tomultipath fading, allow for lower network traffic latencies, providebetter communication efficiencies (such as in terms of bits per secondper unit of bandwidth used, etc.). These and other recent improvementshave facilitated the emergence of the Internet of Things (IOT), largescale Machine to Machine (M2M) communication systems, vehicles, andother technologies that rely on consistent and secure communications.

SUMMARY

The systems, methods and devices of this disclosure each have severalinnovative aspects, no single one of which is solely responsible for thedesirable attributes disclosed herein.

One innovative aspect of the subject matter described in this disclosurecan be implemented in a wireless mobile communication device(hereinafter referred to as “user equipment” or “UE”). Someimplementations may include methods performed by an apparatus of a UEfor operating in a next generation (NG) radio access network (RAN)(NG-RAN). Various implementations may include receiving a systeminformation block (SIB) one (SIB1) from a cell of the NG-RAN,determining whether the cell supports non-public networks (NPNs) basedon the received SIB1, determining whether a NPN-identifier (NPN-ID) inthe received SIB1 matches a NPN-ID in a stored SIB in response todetermining that the cell supports NPNs based on the received SIB1, andvalidating the stored SIB based at least in part on the received SIB1 inresponse to determining that the NPN-ID in the received SIB1 and theNPN-ID associated with the stored SIB match.

In some implementations, determining whether the cell supports NPNsbased on the received SIB1 may involve determining whether the cellsupports only NPNs based on the received SIB1, and determining whether aNPN-identifier (NPN-ID) in the received SIB1 matches an NPN-IDassociated with a stored SIB in response to determining that the cellsupports NPNs based on the received SIB1 may involve determining whetheran NPN-ID in the received SIB1 matches an NPN-ID associated with astored SIB in response to determining that the cell supports only NPNsbased on the received SIB.

Some implementations may further include indicating that the stored SIBis invalid in response to determining that the NPN-ID in the receivedSIB1 and the NPN-ID associated with the stored SIB do not match. In someimplementations, the NPN-ID may be a standalone NPN (SNPN)-identifier(SNPN-ID). In some implementations, the SNPN-ID may include a networkidentifier (NID) and optionally a public land mobile network(PLMN)-identifier (PLMN-ID). In some implementations, the NPN-ID is acombination of a PLMN-ID and a closed access group (CAG)-identifier(CAG-ID). In some implementations, only a first NPN-ID in the receivedSIB and only a first NPN-ID associated with the stored SIB are used todetermine whether the NPN-ID in the received SIB1 matches the NPN-IDassociated with the stored SIB.

Some implementations may further include determining whether an NPN-IDin the received SIB1 indicates that the cell is associated with a SNPNand a network identifier of the SNPN is locally managed. In someimplementations, the NPN-ID in the received SIB1 that indicates that thecell is associated with the SNPN may be a first NPN in the receivedSIB1. Some implementations may further include preventing storage of thereceived SIB1 in response to determining that the NPN-ID in the receivedSIB1 indicates that the cell is associated with a standalone SNPN and anetwork identifier of the SNPN is locally managed. In someimplementations, indicating any stored SIB is invalid in response todetermining that the NPN-ID in the received SIB1 may indicate that thecell is associated with a standalone SNPN and a network identifier ofthe SNPN is locally managed. In some implementations, the networkidentifier of the SNPN being locally managed may be indicated at leastin part by one or more bits of the network identifier of the SNPN.

In some implementations, the SIB1 may be received on a downlink-sharedchannel (DL-SCH). In some implementations, the cell may be a servingcell. In some implementations, the received SIB1 may indicate that thecell supports NPNs by one or more of an information element“cellreservedforotheruse” in the SIB1 set to true and at least oneNPN-ID or CAG-ID indicated in the SIB1, an indication in the SIB1indicates that the cell provides access to NPNs, and only one PLMN-ID isincluded in the information element “PLMN-IdentityInfoList” in the SIB1and the PLMN-ID is a value associated with indicating NPN support.

Another innovative aspect of the subject matter described in thisdisclosure can be implemented in an apparatus of a UE. Someimplementations may include a first interface configured to receive aSIB1 from a cell of the NG-RAN and a processing system coupled to thefirst interface and configured to determine whether the cell supportsNPNs based on the received SIB1, determine whether a NPN-ID in thereceived SIB1 matches an NPN-ID in a stored SIB in response todetermining that the cell supports NPNs based on the received SIB1, andvalidate the stored SIB based at least in part on the received SIB1 inresponse to determining that the NPN-ID in the received SIB1 and theNPN-ID associated with the stored SIB match.

In some implementations, the processing system may determine whether thecell supports NPNs based on the received SIB1 by determining whether thecell supports only NPNs based on the received SIB1, and determinewhether a NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-IDassociated with a stored SIB in response to determining that the cellsupports only NPNs based on the received SIB1.

In some implementations, the processing system may be further configuredto indicate that the stored SIB is invalid in response to determiningthat the NPN-ID in the received SIB1 and the NPN-ID associated with thestored SIB do not match. In some implementations, the processing systemmay be configured such that the NPN-ID may be a SNPN-ID. In someimplementations, the processing system may be configured such that theSNPN-ID may include a network identifier (NID) and optionally a PLMN-ID.In some implementations, the processing system may be configured suchthat the NPN-ID is a combination of a PLMN-ID and a CAG-ID. In someimplementations, the processing system may be configured such that onlya first NPN-ID in the received SIB and only a first NPN-ID associatedwith the stored SIB are used to determine whether the NPN-ID in thereceived SIB1 matches the NPN-ID associated with the stored SIB.

In some implementations, the processing system may be further configuredto determine whether an NPN-ID in the received SIB1 indicates that thecell is associated with a standalone NPN (SNPN) and a network identifierof the SNPN is locally managed. In some implementations, the processingsystem may be configured such that the NPN-ID in the received SIB1 thatindicates that the cell is associated with the SNPN may be a first NPNin the received SIB1. In some implementations, the processing system maybe further configured to prevent storage of the received SIB1 inresponse to determining that the NPN-ID in the received SIB1 indicatesthat the cell is associated with a standalone SNPN and a networkidentifier of the SNPN is locally managed. In some implementations, theprocessing system may be configured such that indicating any stored SIBis invalid in response to determining that the NPN-ID in the receivedSIB1 may indicate that the cell is associated with a standalone SNPN anda network identifier of the SNPN is locally managed. In someimplementations, the processing system may be configured such that thenetwork identifier of the SNPN being locally managed may be indicated atleast in part by one or more bits of the network identifier of the SNPN.

In some implementations, the first interface may be configured such thatthe SIB1 may be received on a DL-SCH. In some implementations, the cellmay be a serving cell. In some implementations, the received SIB1 mayindicate that the cell supports NPNs by one or more of an informationelement “cellreservedforotheruse” in the SIB1 set to true and at leastone NPN-ID or CAG-ID indicated in the SIB1, an indication in the SIB1indicates that the cell only provides access to NPNs, and only onePLMN-ID is included in the information element “PLMN-IdentityInfoList”in the SIB1 and the PLMN-ID is a value associated with indicating NPNsupport.

Another innovative aspect of the subject matter described in thisdisclosure can be implemented in a non-transitory processor-readablemedium having stored thereon processor-executable instructionsconfigured to cause a UE to perform various operations, someimplementations of which may include receiving a SIB1 from a cell of theNG-RAN, determining whether the cell supports NPNs based on the receivedSIB1, determining whether an NPN-ID in the received SIB1 matches aNPN-ID in a stored SIB in response to determining that the cell supportsNPNs based on the received SIB1, and validating the stored SIB based atleast in part on the received SIB1 in response to determining that theNPN-ID in the received SIB1 and the NPN-ID associated with the storedSIB match.

Another innovative aspect of the subject matter described in thisdisclosure can be implemented in a UE that includes means for receivinga SIB1 from a cell of the NG-RAN, means for determining whether the cellsupports NPNs based on the received SIB1, means for determining whetheran NPN-ID in the received SIB1 matches a NPN-ID in a stored SIB inresponse to determining that the cell supports NPNs based on thereceived SIB1, and means for validating the stored SIB based at least inpart on the received SIB1 in response to determining that the NPN-ID inthe received SIB1 and the NPN-ID associated with the stored SIB match.

Details of one or more implementations of the subject matter describedin this disclosure are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages will becomeapparent from the description, the drawings and the claims. Note thatthe relative dimensions of the following figures may not be drawn toscale.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system block diagram illustrating an examplecommunications system.

FIG. 2 shows a component block diagram illustrating an example computingsystem that may be configured to implement operations in a nextgeneration (NG) radio access network (RAN) (NG-RAN).

FIG. 3 shows a component block diagram of an example softwarearchitecture including a radio protocol stack for the user and controlplanes in wireless communications.

FIG. 4 shows a component block diagram illustrating an example systemconfigured for operations in an NG-RAN.

FIG. 5 shows a process flow diagram for an example method forimplementing operations in an NG-RAN by an apparatus of a user equipment(UE).

FIG. 6 shows a process flow diagram for an example method forimplementing operations in an NG-RAN by an apparatus of a UE.

FIG. 7 shows a process flow diagram for an example method forimplementing operations in an NG-RAN by an apparatus of a UE.

FIG. 8 shows a component block diagram of an example network computingdevice.

FIG. 9 shows a component block diagram of an example UE.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

The following description is directed to certain implementations for thepurposes of describing the innovative aspects of this disclosure.However, a person having ordinary skill in the art will readilyrecognize that the teachings herein may be applied in a multitude ofdifferent ways.

The described implementations may be implemented in any device, system,or network that is capable of transmitting and receiving radio frequency(RF) signals according to any of the Institute of Electrical andElectronics Engineers (IEEE) 16.11 standards, or any of the IEEE 802.11standards, the Bluetooth® standard, code division multiple access(CDMA), frequency division multiple access (FDMA), time divisionmultiple access (TDMA), Global System for Mobile communications (GSM),GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment(EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA),Evolution Data Optimized (EV-DO), 1×EV-DO, EV-DO Rev A, EV-DO Rev B,High Speed Packet Access (HSPA), High Speed Downlink Packet Access(HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High SpeedPacket Access (HSPA+), Long Term Evolution (LTE), AMPS, or other signalsthat are used to communicate within a wireless, cellular or Internet ofThings (IoT) network, such as a system utilizing 3G, 4G, or 5Gtechnology, or further implementations thereof.

Various implementations described in this disclosure include methodsperformed by an apparatus (such as a processing system) of a UE forimplementing operations in a next generation (NG) radio access network(RAN) (NG-RAN).

Some implementations may provide an enhancement to a validity check of asystem information block (SIB, such as a SIB1, SIB3, SIB4, etc.). Insome implementations, if a cell provides access to NPNs, an NPN-ID (suchas a SNPN-ID or PLMN-ID+CAG-ID) broadcast in a SIB1 may be used for aSIB validity check. In some implementations, the first NPN-ID broadcastin the SIB1 may be used for SIB validity checks. In someimplementations, an NPN-ID other than the first NPN-ID broadcast in theSIB1 may be used for SIB validity checks. In some implementations, ifthe cell doesn't provide access to only NPNs, the first PLMN-ID in thePLMN-IdentityInfoList element of the SIB1 may be used for a SIB validitycheck. As an example, a cell that only provides access to NPNs may be anNPN-only cell.

In some implementations, a cell may be determined to provide access onlyto NPNs based on one or more of the following: 1) the cell broadcastinga cellreservedforotheruse information element set to true andbroadcasting at least one of a network identifier (NID) or CAG-ID; 2)the cell broadcasting an indication to indicate that the cell providesaccess only to NPNs; or 3) only one PLMN-ID being included in thePLMN-IdentityInfoList element and set to a specific Third GenerationPartnership Project (3GPP) value.

In some implementations, a UE may not store a SIB from a cell if anNPN-ID in the SIB (such as the first NPN-ID or an NPN-ID other than thefirst NPN-ID) is associated with a SNPN and the associated broadcastedNID is a locally managed one.

In some implementations, a UE may consider a stored SIB to be invalid anNPN-ID in the SIB (such as the first NPN-ID or an NPN-ID other than thefirst NPN-ID) is associated with a SNPN and the associated broadcastedNID is a locally managed one.

Particular implementations of the subject matter described in thisdisclosure can be implemented to realize one or more of the followingpotential advantages. Some implementations may improve operations of aUE to validate stored SIBs, specifically stored SIBs associated withNPNs. Validating stored SIBs may enable faster system information (SI)acquisition after events triggering SI acquisition (such as after cellre-selection, upon return from out of coverage, after reception of an SIchange indication, etc.) because valid SIBs may be reused, rather thanrequiring the UE to download the already stored valid SIBs. Someimplementations may improve the operations of a UE in a SNPN that isassociated with a locally managed NID by preventing misuse of a wrongSIB due to collision or confusion between NIDs and thereby preventingunwanted emissions that may violate emission settings or regulations.

The terms “wireless device” or “computing device” are usedinterchangeably herein to refer to any one or all of wireless routerdevices, wireless appliances, cellular telephones, smartphones, portablecomputing devices, personal or mobile multi-media players, laptopcomputers, tablet computers, smartbooks, ultrabooks, palmtop computers,wireless electronic mail receivers, multimedia Internet-enabled cellulartelephones, medical devices and equipment, biometric sensors/devices,wearable devices including smart watches, smart clothing, smart glasses,smart wrist bands, smart jewelry (for example smart rings, smartbracelets, etc.), entertainment devices (for example wireless gamingcontrollers, music and video players, satellite radios, etc.),wireless-network enabled Internet of Things (IoT) devices includingsmart meters/sensors, industrial manufacturing equipment, large andsmall machinery and appliances for home or enterprise use, wirelesscommunication elements within vehicles, wireless devices affixed to orincorporated into various mobile platforms, global positioning systemdevices, and similar electronic devices that include a memory, wirelesscommunication components and a programmable apparatus (such as aprocessing system).

The term “system on chip” (SOC) is used herein to refer to a singleintegrated circuit (IC) chip that contains an apparatus (such as aprocessing system) of multiple resources or processors integrated on asingle substrate. A single SOC may contain circuitry for digital,analog, mixed-signal, and radio-frequency functions. A single SOC alsomay include any number of general purpose or specialized processors(digital signal processors, modem processors, video processors, etc.),memory blocks (for example ROM, RAM, Flash, etc.), and resources (forexample timers, voltage regulators, oscillators, etc.). SOCs also mayinclude software for controlling the integrated resources andprocessors, as well as for controlling peripheral devices.

The term “system in a package” (SIP) may be used herein to refer to asingle module or package that contains an apparatus (such as aprocessing system) of multiple resources, computational units, cores orprocessors on two or more IC chips, substrates, or SOCs. For example, aSIP may include a single substrate on which multiple IC chips orsemiconductor dies are stacked in a vertical configuration. Similarly,the SIP may include one or more multi-chip modules (MCMs) on whichmultiple ICs or semiconductor dies are packaged into a unifyingsubstrate. A SIP also may include multiple independent SOCs coupledtogether via high speed communication circuitry and packaged in closeproximity, such as on a single motherboard or in a single wirelessdevice. The proximity of the SOCs facilitates high speed communicationsand the sharing of memory and resources.

The term “multicore processor” may be used herein to refer to a singleintegrated circuit (IC) chip or chip package that contains two or moreindependent processing cores (for example CPU core, Internet protocol(IP) core, graphics processor unit (GPU) core, etc.) configured to readand execute program instructions. A SOC may include multiple multicoreprocessors, and each processor in an SOC may be referred to as a core.The term “multiprocessor” may be used herein to refer to a system ordevice that includes two or more processing units configured to read andexecute program instructions.

The term “processing system” is used herein to refer to a processor, aSOC, or a SIP, coupled to or including a memory device.

FIG. 1 shows a system block diagram illustrating an examplecommunications system 100. The communications system 100 may be a 5G NRnetwork (such as a next generation (NG) radio access network (RAN)(NG-RAN)), or any other suitable network such as an LTE network.

The communications system 100 may include a heterogeneous networkarchitecture that includes a core network 140 and a variety of mobiledevices (illustrated as wireless device 120 a-120 e in FIG. 1). Thecommunications system 100 also may include a number of base stations(illustrated as the BS 110 a, the BS 110 b, the BS 110 c, and the BS 110d) and other network entities. A base station is an entity thatcommunicates with wireless devices (mobile devices or UE computingdevices), and also may be referred to as an NodeB, a Node B, an LTEevolved nodeB (eNB), an access point (AP), a radio head, a transmitreceive point (TRP), a New Radio base station (NR BS), a 5G NodeB (NB),a Next Generation NodeB (gNB), or the like. Each base station mayprovide communication coverage for a particular geographic area. In3GPP, the term “cell” can refer to a coverage area of a base station, abase station subsystem serving this coverage area, or a combinationthereof, depending on the context in which the term is used.

A base station 110 a-110 d may provide communication coverage for amacro cell, a pico cell, a femto cell, another type of cell, or acombination thereof. A macro cell may cover a relatively largegeographic area (for example, several kilometers in radius) and mayallow unrestricted access by mobile devices with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by mobile devices with service subscription. A femtocell may cover a relatively small geographic area (for example, a home)and may allow restricted access by mobile devices having associationwith the femto cell (for example, mobile devices in a closed subscribergroup (CSG)). A base station for a macro cell may be referred to as amacro BS. A base station for a pico cell may be referred to as a picoBS. A base station for a femto cell may be referred to as a femto BS ora home BS. In the example illustrated in FIG. 1, a base station 110 amay be a macro BS for a macro cell 102 a, a base station 110 b may be apico BS for a pico cell 102 b, and a base station 110 c may be a femtoBS for a femto cell 102 c. A base station 110 a-110 d may support one ormultiple (for example, three) cells. The terms “eNB”, “base station”,“NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” may be usedinterchangeably herein.

In some examples, a cell may not be stationary, and the geographic areaof the cell may move according to the location of a mobile base station.In some examples, the base stations 110 a-110 d may be interconnected toone another as well as to one or more other base stations or networknodes (not illustrated) in the communications system 100 through varioustypes of backhaul interfaces, such as a direct physical connection, avirtual network, or a combination thereof using any suitable transportnetwork

The base station 110 a-110 d may communicate with the core network 140over a wired or wireless communication link 126. The wireless device 120a-120 e (or UE computing device) may communicate with the base station110 a-110 d over a wireless communication link 122.

The wired communication link 126 may use a variety of wired networks(for example Ethernet, TV cable, telephony, fiber optic and other formsof physical network connections) that may use one or more wiredcommunication protocols, such as Ethernet, Point-To-Point protocol,High-Level Data Link Control (HDLC), Advanced Data Communication ControlProtocol (ADCCP), and Transmission Control Protocol/Internet Protocol(TCP/IP).

The communications system 100 also may include relay stations (forexample relay BS 110 d). A relay station is an entity that can receive atransmission of data from an upstream station (for example, a basestation or a mobile device) and send a transmission of the data to adownstream station (for example, a wireless device or a base station). Arelay station also may be a mobile device that can relay transmissionsfor other wireless devices. In the example illustrated in FIG. 1, arelay station 110 d may communicate with macro the base station 110 aand the wireless device 120 d in order to facilitate communicationbetween the base station 110 a and the wireless device 120 d. A relaystation also may be referred to as a relay base station, a relay basestation, a relay, etc.

The communications system 100 may be a heterogeneous network thatincludes base stations of different types, for example, macro basestations, pico base stations, femto base stations, relay base stations,etc. These different types of base stations may have different transmitpower levels, different coverage areas, and different impacts oninterference in communications system 100. For example, macro basestations may have a high transmit power level (for example, 5 to 40Watts) whereas pico base stations, femto base stations, and relay basestations may have lower transmit power levels (for example, 0.1 to 2Watts).

A network controller 130 may couple to a set of base stations and mayprovide coordination and control for these base stations. The networkcontroller 130 may communicate with the base stations via a backhaul.The base stations also may communicate with one another, for example,directly or indirectly via a wireless or wireline backhaul.

The wireless devices (UE computing devices) 120 a, 120 b, 120 c may bedispersed throughout communications system 100, and each wireless devicemay be stationary or mobile. A wireless device also may be referred toas an access terminal, a terminal, a mobile station, a subscriber unit,a station, etc.

A macro base station 110 a may communicate with the communicationnetwork 140 over a wired or wireless communication link 126. Thewireless devices 120 a, 120 b, 120 c may communicate with a base station110 a-110 d over a wireless communication link 122.

Wired communication links may use a variety of wired networks (such asEthernet, TV cable, telephony, fiber optic and other forms of physicalnetwork connections) that may use one or more wired communicationprotocols, such as Ethernet, Point-To-Point protocol, High-Level DataLink Control (HDLC), Advanced Data Communication Control Protocol(ADCCP), and Transmission Control Protocol/Internet Protocol (TCP/IP).

The wireless communication links 122, 124 may include a plurality ofcarrier signals, frequencies, or frequency bands, each of which mayinclude a plurality of logical channels. The wireless communicationlinks 122 and 124 may utilize one or more radio access technologies(RATs). Examples of RATs that may be used in a wireless communicationlink include 3GPP LTE, 3G, 4G, 5G (for example NR), GSM, Code DivisionMultiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA),Worldwide Interoperability for Microwave Access (WiMAX), Time DivisionMultiple Access (TDMA), and other mobile telephony communicationtechnologies cellular RATs. Further examples of RATs that may be used inone or more of the various wireless communication links 122, 124 withinthe communication system 100 include medium range protocols such asWi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire, and relatively short rangeRATs such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE).

Certain wireless networks (such as LTE) utilize orthogonal frequencydivision multiplexing (OFDM) on the downlink and single-carrierfrequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDMpartition the system bandwidth into multiple (K) orthogonal subcarriers,which are also commonly referred to as tones, bins, etc. Each subcarriermay be modulated with data. In general, modulation symbols are sent inthe frequency domain with OFDM and in the time domain with SC-FDM. Thespacing between adjacent subcarriers may be fixed, and the total numberof subcarriers (K) may be dependent on the system bandwidth. Forexample, the spacing of the subcarriers may be 15 kHz and the minimumresource allocation (called a “resource block”) may be 12 subcarriers(or 180 kHz). Consequently, the nominal Fast File Transfer (FFT) sizemay be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively. The systembandwidth also may be partitioned into subbands. For example, a subbandmay cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4,8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz,respectively.

Certain wireless networks in the communications system 100 may benon-public networks (NPNs) for non-public use. NPNs may includedifferent types of networks. Some NPNs may be stand-alone non-publicnetworks (SNPNs) that may be operated by an NPN operator and not rely onnetwork functions provided by a public land mobile network (PLMN). SomeNPNs may be public network integrated NPNs (PNI-NPNs) that may benon-public networks deployed with the support of PLMNs. PNI-NPNs may bedeployed in different manners. One deployment for PNI-NPNs may includeusing slicing by allocating a network slice to an NPN. Anotherdeployment for PNI-NPNs may include using closed access groups (CAGs).

While descriptions of some implementations may use terminology andexamples associated with LTE technologies, some implementations may beapplicable to other wireless communications systems, such as a new radio(NR) or 5G network. NR may utilize OFDM with a cyclic prefix (CP) on theuplink (UL) and downlink (DL) and include support for half-duplexoperation using time division duplex (TDD). A single component carrierbandwidth of 100 MHz may be supported. NR resource blocks may span 12sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1milliseconds (ms) duration. Each radio frame may consist of 50 subframeswith a length of 10 msec. Consequently, each subframe may have a lengthof 0.2 msec. Each subframe may indicate a link direction (i.e., DL orUL) for data transmission and the link direction for each subframe maybe dynamically switched. Each subframe may include DL/UL data as well asDL/UL control data. Beamforming may be supported and beam direction maybe dynamically configured. Multiple Input Multiple Output (MIMO)transmissions with precoding also may be supported. MIMO configurationsin the DL may support up to eight transmit antennas with multi-layer DLtransmissions up to eight streams and up to two streams per wirelessdevice. Multi-layer transmissions with up to 2 streams per wirelessdevice may be supported. Aggregation of multiple cells may be supportedwith up to eight serving cells. Alternatively, NR may support adifferent air interface, other than an OFDM-based air interface.

Some mobile devices may be considered machine-type communication (MTC)or evolved or enhanced machine-type communication (eMTC) mobile devices.MTC and eMTC mobile devices include, for example, robots, remotedevices, sensors, meters, monitors, location tags, etc., that maycommunicate with a base station, another device (for example, remotedevice), or some other entity. A wireless node may provide, for example,connectivity for or to a network (for example, a wide area network suchas Internet or a cellular network) via a wired or wireless communicationlink. Some mobile devices may be considered Internet-of-Things (IoT)devices or may be implemented as NB-IoT (narrowband internet of things)devices. A wireless device 120 a-120 e may be included inside a housingthat houses components of the wireless device, such as processorcomponents, memory components, similar components, or a combinationthereof.

In general, any number of communications systems and any number ofwireless networks may be deployed in a given geographic area. Eachcommunications system and wireless network may support a particularradio access technology (RAT) and may operate on one or morefrequencies. A RAT also may be referred to as a radio technology, an airinterface, etc. A frequency also may be referred to as a carrier, afrequency channel, etc. Each frequency may support a single RAT in agiven geographic area in order to avoid interference betweencommunications systems of different RATs. In some cases, NR or 5G RATnetworks may be deployed.

In some examples, access to the air interface may be scheduled, where ascheduling entity (for example, a base station) allocates resources forcommunication among some or all devices and equipment within thescheduling entity's service area or cell. The scheduling entity may beresponsible for scheduling, assigning, reconfiguring, and releasingresources for one or more subordinate entities. That is, for scheduledcommunication, subordinate entities utilize resources allocated by thescheduling entity.

Base stations are not the only entities that may function as ascheduling entity. In some examples, a wireless device may function as ascheduling entity, scheduling resources for one or more subordinateentities (for example, one or more other mobile devices). In thisexample, the wireless device is functioning as a scheduling entity, andother mobile devices utilize resources scheduled by the wireless devicefor wireless communication. A wireless device may function as ascheduling entity in a peer-to-peer (P2P) network, in a mesh network, oranother type of network. In a mesh network example, mobile devices mayoptionally communicate directly with one another in addition tocommunicating with the scheduling entity.

Thus, in a wireless communication network with a scheduled access totime-frequency resources and having a cellular configuration, a P2Pconfiguration, and a mesh configuration, a scheduling entity and one ormore subordinate entities may communicate utilizing the scheduledresources.

In some implementations, two or more mobile devices 120 a-120 e (forexample, illustrated as the wireless device 120 a and the wirelessdevice 120 e) may communicate directly using one or more sidelinkchannels 124 (for example, without using a base station 110 a-110 d asan intermediary to communicate with one another). For example, thewireless devices 120 a-120 e may communicate using peer-to-peer (P2P)communications, device-to-device (D2D) communications, avehicle-to-everything (V2X) protocol (which may include avehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I)protocol, or similar protocol), a mesh network, or similar networks, orcombinations thereof. In this case, the wireless device 120 a-120 e mayperform scheduling operations, resource selection operations, as well asother operations described elsewhere herein as being performed by thebase station 110 a.

FIG. 2 shows a component block diagram illustrating an example computingsystem that may be configured to implement operations in an NG-RAN. Someimplementations may be implemented on a number of single processor andmultiprocessor computer systems, including a system-on-chip (SOC) orsystem in a package (SIP). FIG. 2 shows an example computing system orSIP 200 architecture that may be used in wireless devices (UE computingdevices) implementing the various implementations.

With reference to FIGS. 1 and 2, the illustrated example SIP 200includes a two SOCs 202, 204, a clock 206, and a voltage regulator 208.In some implementations, the first SOC 202 operate as central processingunit (CPU) of the wireless device that carries out the instructions ofsoftware application programs by performing the arithmetic, logical,control and input/output (I/O) operations specified by the instructions.In some implementations, the second SOC 204 may operate as a specializedprocessing unit. For example, the second SOC 204 may operate as aspecialized 5G processing unit responsible for managing high volume,high speed (for example 5 Gbps, etc.), or very high frequency shortwavelength (for example 28 GHz mmWave spectrum, etc.) communications.

The first SOC 202 may include a digital signal processor (DSP) 210, amodem processor 212, a graphics processor 214, an application processor216, one or more coprocessors 218 (for example vector co-processor)connected to one or more of the processors, memory 220, custom circuitry222, system components and resources 224, an interconnection/bus module226, one or more temperature sensors 230, a thermal management unit 232,and a thermal power envelope (TPE) component 234. The second SOC 204 mayinclude a 5G modem processor 252, a power management unit 254, aninterconnection/bus module 264, a plurality of mmWave transceivers 256,memory 258, and various additional processors 260, such as anapplications processor, packet processor, etc.

Each processor 210, 212, 214, 216, 218, 252, 260 in an apparatus (suchas a processing system) may include one or more cores, and eachprocessor/core may perform operations independent of the otherprocessors/cores. For example, the first SOC 202 may include a processorthat executes a first type of operating system (for example FreeBSD,LINUX, OS X, etc.) and a processor that executes a second type ofoperating system (for example MICROSOFT WINDOWS 10). In addition, any orall of the processors 210, 212, 214, 216, 218, 252, 260 may be includedas part of a processor cluster architecture (for example a synchronousprocessor cluster architecture, an asynchronous or heterogeneousprocessor cluster architecture, etc.).

The first and second SOC 202, 204 may include various system components,resources and custom circuitry for managing sensor data,analog-to-digital conversions, wireless data transmissions, and forperforming other specialized operations, such as decoding data packetsand processing encoded audio and video signals for rendering in a webbrowser. For example, the system components and resources 224 of thefirst SOC 202 may include power amplifiers, voltage regulators,oscillators, phase-locked loops, peripheral bridges, data controllers,memory controllers, system controllers, access ports, timers, and othersimilar components used to support the processors and software clientsrunning on a wireless device. The system components and resources 224 orcustom circuitry 222 also may include circuitry to interface withperipheral devices, such as cameras, electronic displays, wirelesscommunication devices, external memory chips, etc.

The first and second SOC 202, 204 may communicate viainterconnection/bus module 250. The various processors 210, 212, 214,216, 218, may be interconnected to one or more memory elements 220,system components and resources 224, and custom circuitry 222, and athermal management unit 232 via an interconnection/bus module 226.Similarly, the processor 252 may be interconnected to the powermanagement unit 254, the mmWave transceivers 256, memory 258, andvarious additional processors 260 via the interconnection/bus module264. The interconnection/bus module 226, 250, 264 may include an arrayof reconfigurable logic gates or implement a bus architecture (forexample CoreConnect, AMBA, etc.). Communications may be provided byadvanced interconnects, such as high-performance networks-on chip(NoCs).

The first or second SOCs 202, 204 may further include an input/outputmodule (not illustrated) for communicating with resources external tothe SOC, such as a clock 206 and a voltage regulator 208. Resourcesexternal to the SOC (for example clock 206, voltage regulator 208) maybe shared by two or more of the internal SOC processors/cores.

In addition to the example SIP 200 discussed above, some implementationsmay be implemented in a wide variety of processing systems, which mayinclude a single processor, multiple processors, multicore processors,or any combination thereof.

FIG. 3 shows a component block diagram of an example softwarearchitecture including a radio protocol stack for the user and controlplanes in wireless communications. FIG. 3 shows an example of a softwarearchitecture 300 including a radio protocol stack for the user andcontrol planes in wireless communications between a base station 350(for example the base station 110 a) and a wireless device 120 (forexample the wireless device (UE computing device) 120 a-120 e, 200).With reference to FIGS. 1-3, the wireless device 120 may implement thesoftware architecture 300 to communicate with the base station 350 of acommunication system (for example 100). In some implementations, layersin software architecture 300 may form logical connections withcorresponding layers in software of the base station 350. The softwarearchitecture 300 may be distributed among one or more processing systems(for example the processors 212, 214, 216, 218, 252, 260). Whileillustrated with respect to one radio protocol stack, in a multi-SIM(subscriber identity module) wireless device, the software architecture300 may include multiple protocol stacks, each of which may beassociated with a different SIM (for example two protocol stacksassociated with two SIMs, respectively, in a dual-SIM wirelesscommunication device). While described below with reference to specific5G-NR communication layers, the software architecture 300 may supportany of variety of standards and protocols for wireless communications,or may include additional protocol stacks that support any of variety ofstandards and protocols wireless communications.

The software architecture 300 may include a Non-Access Stratum (NAS) 302and an Access Stratum (AS) 304. The NAS 302 may include functions andprotocols to support packet filtering, security management, mobilitycontrol, session management, and traffic and signaling between a SIM(s)of the wireless device (for example SIM(s) 204) and its core network140. The AS 304 may include functions and protocols that supportcommunication between a SIM(s) (for example SIM(s) 204) and entities ofsupported access networks (for example a base station). In particular,the AS 304 may include at least three layers (Layer 1, Layer 2, andLayer 3), each of which may contain various sub-layers.

In the user and control planes, Layer 1 (L1) of the AS 304 may be aphysical layer (PHY) 306, which may oversee functions that enabletransmission or reception over the air interface. Examples of suchphysical layer 306 functions may include cyclic redundancy check (CRC)attachment, coding blocks, scrambling and descrambling, modulation anddemodulation, signal measurements, MIMO, etc. The physical layer mayinclude various logical channels, including the Physical DownlinkControl Channel (PDCCH) and the Physical Downlink Shared Channel(PDSCH).

In the user and control planes, Layer 2 (L2) of the AS 304 may beresponsible for the link between the wireless device 120 and the basestation 350 over the physical layer 306. In some implementations, Layer2 may include a media access control (MAC) sublayer 308, a radio linkcontrol (RLC) sublayer 310, and a packet data convergence protocol(PDCP) 312 sublayer, and a Service Data Adaptation Protocol (SDAP) 317sublayer, each of which form logical connections terminating at the basestation 350.

In the control plane, Layer 3 (L3) of the AS 304 may include a radioresource control (RRC) sublayer 3. While not shown, the softwarearchitecture 300 may include additional Layer 3 sublayers, as well asvarious upper layers above Layer 3. In some implementations, the RRCsublayer 313 may provide functions INCLUDING broadcasting systeminformation, paging, and establishing and releasing an RRC signalingconnection between the wireless device 120 and the base station 350.

In some implementations, the SDAP sublayer 317 may provide mappingbetween Quality of Service (QoS) flows and data radio bearers (DRBs). Inthe downlink, at the base station 350, the SDAP sublayer 317 may providemapping for DL QoS flows to DRBs. In the uplink, at the wireless device120, the SDAP sublayer 317 may deliver DL received QoS flows to upperlayers. In some implementations, the PDCP sublayer 312 may provideuplink functions including multiplexing between different radio bearersand logical channels, sequence number addition, handover data handling,integrity protection, ciphering, and header compression. In thedownlink, the PDCP sublayer 312 may provide functions that includein-sequence delivery of data packets, duplicate data packet detection,integrity validation, deciphering, and header decompression.

In the uplink, the RLC sublayer 310 may provide segmentation andconcatenation of upper layer data packets, retransmission of lost datapackets, and Automatic Repeat Request (ARQ). In the downlink, while theRLC sublayer 310 functions may include reordering of data packets tocompensate for out-of-order reception, reassembly of upper layer datapackets, and ARQ.

In the uplink, MAC sublayer 308 may provide functions includingmultiplexing between logical and transport channels, random accessprocedure, logical channel priority, and hybrid-ARQ (HARQ) operations.In the downlink, the MAC layer functions may include channel mappingwithin a cell, de-multiplexing, discontinuous reception (DRX), and HARQoperations.

While the software architecture 300 may provide functions to transmitdata through physical media, the software architecture 300 may furtherinclude at least one host layer 314 to provide data transfer services tovarious applications in the wireless device 120. In someimplementations, application-specific functions provided by the at leastone host layer 314 may provide an interface between the softwarearchitecture and the general purpose processor 206.

In some other implementations, the software architecture 300 may includeone or more higher logical layer (for example transport, session,presentation, application, etc.) that provide host layer functions. Forexample, in some implementations, the software architecture 300 mayinclude a network layer (for example IP layer) in which a logicalconnection terminates at an access and mobility factor (AMF) or packetdata network (PDN) gateway (PGW). In some implementations, the softwarearchitecture 300 may include an application layer in which a logicalconnection terminates at another device (for example end user device,server, etc.). In some implementations, the software architecture 300may further include in the AS 304 a hardware interface 316 between thephysical layer 306 and the communication hardware (for example one ormore radio frequency (RF) transceivers).

FIG. 4 shows a component block diagram illustrating an example systemconfigured for operations in an NG-RAN. In some implementations, thesystem 400 that may be implemented in a UE may an apparatus 402. Withreference to FIGS. 1-4, the apparatus 402 may be implemented in a UE(for example the wireless devices 120, 120 a-120 e, 200). The remoteplatform(s) 404 may include a base station (for example the base station110 a-110 d, 350) or a wireless device (for example the wireless device120, 120 a-120 e, 200).

The apparatus 402 may be configured by machine-readable instructions406. Machine-readable instructions 406 may include one or moreinstruction modules. The instruction modules may include computerprogram modules. The instruction modules may include one or more of cellreceiving module 408, cell determination module 410, network-identifierdetermination module 412, SIB indicating module 414, SIB validationmodule 416, storage preventing module 418, or other instruction modules.

Cell receiving module 408 may be configured to receive a SIB1 from acell of the next generation radio access network. The cell may be aserving cell. In some implementations, the SIB1 may be received on adownlink-shared channel (DL-SCH).

Cell determination module 410 may be configured to determine whether thecell supports a non-public network (NPN) based on the received SIB1. Insome aspects, the cell determination module 410 may be configured todetermine whether the cell supports only a non-public network (NPN)based on the received SIB1.

Network-identifier determination module 412 may be configured todetermine whether an NPN-identifier (NPN-ID) in the received SIB1matches an NPN-identifier in a stored SIB in response to determiningthat the cell supports an NPN based on the received SIB1. In someaspects, the network-identifier determination module 412 may beconfigured to determine whether an NPN-identifier (NPN-ID) in thereceived SIB1 matches an NPN-identifier in a stored SIB in response todetermining that the cell supports only an NPN based on the receivedSIB1.

Network-identifier determination module 412 may be configured todetermine whether an NPN-ID in the received SIB1 indicates that the cellis associated with a standalone NPN (SNPN) and a network identifier ofthe SNPN is locally managed.

Network-identifier determination module 412 may be configured todetermine whether an NPN-ID in the received SIB1 indicates that the cellis associated with a SNPN and a network identifier of the SNPN islocally managed. The NPN-ID may be a SNPN-ID. The SIB1 may be receivedon a DL-SCH. The NPN-ID may be a combination of a public land mobilenetwork (PLMN)-identifier (PLMN-ID) and a closed access group(CAG)-identifier (CAG-ID). The SIB1 may be received on a DL-SCH.

SIB indicating module 414 may be configured to indicate that the storedSIB is invalid in response to determining that the NPN-ID in thereceived SIB1 and the NPN-ID associated with the stored SIB do notmatch.

SIB indicating module 414 may be configured to indicate any stored SIBis invalid in response to determining that the NPN-ID in the receivedSIB1 indicates that the cell is associated with a SNPN and a networkidentifier of the SNPN is locally managed.

SIB validation module 416 may be configured to validate the stored SIBbased at least in part on the received SIB1 in response to determiningthat the NPN-ID in the received SIB1 and the NPN-ID associated with thestored SIB match.

Storage preventing module 418 may be configured to prevent storage ofthe received SIB1 in response to determining that the NPN-ID in thereceived SIB1 indicates that the cell is associated with a SNPN and anetwork identifier of the SNPN is locally managed.

FIG. 5 shows a process flow diagram for an example method forimplementing operations in an NG-RAN by an apparatus (such as aprocessing system) of a UE. With reference to FIGS. 1-5, the method 500may be implemented by an apparatus (such as a processing system) (suchas 212, 216, 252 or 260) of a UE (such as the wireless device 120, 120a-120 e, 200). The operations of method 500 may be performed inconjunction with the operations of method 600 or method 700.

In block 502, the apparatus (such as a processing system) may performoperations including receiving a SIB1 from a cell of the next generationradio access network. In some aspects, the SIB1 may be received on adownlink-shared channel (DL-SCH). In some aspects, the cell may be aserving cell.

In block 504, the apparatus (such as a processing system) may performoperations including determining whether the cell supports NPNs based onthe received SIB1. In some aspects, the apparatus (such as a processingsystem) may determine whether the cell supports only NPNs based on thereceived SIB1. In some aspects, the received SIB1 may indicate that thecell supports NPNs or only NPNs by one or more of an information element“cellreservedforotheruse” in the SIB1 set to true and at least oneNPN-ID or CAG-ID indicated in the SIB1, an indication in the SIB1indicates that the cell only provides access to NPNs, and only onePLMN-ID is included in the information element “PLMN-IdentityInfoList”in the SIB1 and the PLMN-ID is a value associated with indicating NPNsupport.

In determination block 506, the apparatus (such as a processing system)may perform operations to determine whether an NPN-ID in the receivedSIB1 matches an NPN-ID in a stored SIB in response to determining thatthe cell supports NPNs based on the received SIB1. In some aspects, theapparatus (such as a processing system) may perform operations todetermine whether an NPN-ID in the received SIB1 matches an NPN-ID in astored SIB in response to determining that the cell supports only NPNsbased on the received SIB1. In some aspects, the NPN-ID may be astandalone NPN (SNPN)-identifier (SNPN-ID). In some aspects, the SNPN-IDmay include a network identifier (NID) and optionally a public landmobile network (PLMN)-identifier (PLMN-ID). In some aspects, the NPN-IDis a combination of a public land mobile network (PLMN)-identifier(PLMN-ID) and a closed access group (CAG)-identifier (CAG-ID). In someaspects, only a first NPN-ID in the received SIB and only a first NPN-IDassociated with the stored SIB are used to determine whether the NPN-IDin the received SIB1 matches the NPN-ID associated with the stored SIB.

In response to determining that the NPN-ID in the received SIB1 and theNPN-ID associated with the stored SIB do not match (i.e., determinationblock 506=No (or No match)), the apparatus (such as a processing system)may perform operations including validating the stored SIB based atleast in part on the received SIB1 in block 512 indicating that thestored SIB is invalid in block 508, and as a result, the apparatus (suchas a processing system) will obtain a new SIB according to standardprotocol procedures in block 510.

In response to determining that the NPN-ID in the received SIB1 and theNPN-ID associated with the stored SIB do match (i.e., determinationblock 506=Yes (or Yes match)), the apparatus (such as a processingsystem) may perform operations including validating the stored SIB basedat least in part on the received SIB1 in block 512.

FIG. 6 shows a process flow diagram for an example method forimplementing operations in an NG-RAN by an apparatus (such as aprocessing system) of a UE. With reference to FIGS. 1-6, the method 600may be implemented by an apparatus (such as a processing system) (suchas 212, 216, 252 or 260) of a UE (such as the wireless device 120, 120a-120 e, 200). The operations of method 600 may be performed inconjunction with the operations of method 500 or method 700.

In block 502, the apparatus (such as a processing system) may performoperations including receiving a SIB1 from a cell of the next generationradio access network as described for the like number block of themethod 500 (FIG. 5). In some aspects, the SIB1 may be received on adownlink-shared channel (DL-SCH). In some aspects, the cell may be aserving cell.

In block 504, the apparatus (such as a processing system) may performoperations including determining whether the cell supports NPNs based onthe received SIB1 as described for the like number block of the method500 (FIG. 5). In some aspects, determining whether the cell supportsNPNs based on the received SIB1 may include determining whether the cellsupports only NPNs based on the received SIB1. In some aspects, thereceived SIB1 may indicate that the cell supports only NPNs by one ormore of an information element “cellreservedforotheruse” in the SIB1 setto true and at least one NPN-ID or CAG-ID indicated in the SIB1, anindication in the SIB1 indicates that the cell only provides access toNPNs, and only one PLMN-ID is included in the information element“PLMN-IdentityInfoList” in the SIB1 and the PLMN-ID is a valueassociated with indicating NPN support.

In block 602, the apparatus (such as a processing system) may performoperations including determining whether an NPN-ID in the received SIB1indicates that the cell is associated with a SNPN and a networkidentifier of the SNPN is locally managed. In some aspects, the NPN-IDin the received SIB1 that indicates that the cell is associated with theSNPN may be a first NPN in the received SIB1. In some aspects, thenetwork identifier of the SNPN being locally managed may be indicated atleast in part by one or more bits of the network identifier of the SNPN.

In block 604, the apparatus (such as a processing system) may performoperations including preventing storage of the received SIB1 in responseto determining that the NPN-ID in the received SIB1 indicates that thecell is associated with a SNPN and a network identifier of the SNPN islocally managed.

FIG. 7 shows a process flow diagram for an example method forimplementing operations in an NG-RAN by an apparatus (such as aprocessing system) of a UE. With reference to FIGS. 1-7, the method 700may be implemented by an apparatus (such as a processing system) (suchas 212, 216, 252 or 260) of a UE (such as the wireless device 120, 120a-120 e, 200). The operations of method 700 may be performed inconjunction with the operations of the method 500 or the method 600.

In block 502, the apparatus (such as a processing system) may performoperations including receiving a SIB1 from a cell of the next generationradio access network as described for the like number block of themethod 500 (FIG. 5). In some aspects, the SIB1 may be received on adownlink-shared channel (DL-SCH). In some aspects, the cell may be aserving cell.

In block 504, the apparatus (such as a processing system) may performoperations including determining whether the cell supports NPNs based onthe received SIB1 as described for the like number block of the method500 (FIG. 5). In some aspects, determining whether the cell supportsNPNs based on the received SIB1 may include determining whether the cellsupports only NPNs based on the received SIB1. In some aspects, thereceived SIB1 may indicate that the cell supports only NPNs by one ormore of an information element “cellreservedforotheruse” in the SIB1 setto true and at least one NPN-ID or CAG-ID indicated in the SIB1, anindication in the SIB1 indicates that the cell only provides access toNPNs, and only one PLMN-ID is included in the information element“PLMN-IdentityInfoList” in the SIB1 and the PLMN-ID is a valueassociated with indicating NPN support.

In block 602, the apparatus (such as a processing system) may performoperations including determining whether an NPN-ID in the received SIB1indicates that the cell is associated with a SNPN and a networkidentifier of the SNPN is locally managed as described for the likenumber block of the method 600 (FIG. 6). In some aspects, the NPN-ID inthe received SIB1 that indicates that the cell is associated with theSNPN may be a first NPN in the received SIB1. In some aspects, thenetwork identifier of the SNPN being locally managed may be indicated atleast in part by one or more bits of the network identifier of the SNPN.

In block 702, the apparatus (such as a processing system) may performoperations including indicating any stored SIB is invalid in response todetermining that the NPN-ID in the received SIB1 indicates that the cellis associated with a SNPN and a network identifier of the SNPN islocally managed.

FIG. 8 shows a component block diagram of an example network computingdevice 800. Some implementations may be implemented on a variety ofwireless network devices, an example of which is illustrated in FIG. 8in the form of a wireless network computing device 800 functioning as anetwork element of a communication network, such as a base station. Suchnetwork computing devices may include at least the componentsillustrated in FIG. 8. With reference to FIGS. 1-8, the networkcomputing device 800 may typically include an apparatus (such as aprocessing system) 801 coupled to volatile memory 802 and a largecapacity nonvolatile memory, such as a disk drive 803. The networkcomputing device 800 also may include a peripheral memory access devicesuch as a floppy disc drive, compact disc (CD) or digital video disc(DVD) drive 806 coupled to the apparatus (such as a processing system)801. The network computing device 800 also may include network accessports 804 (or interfaces) coupled to the apparatus (such as a processingsystem) 801 for establishing data connections with a network, such asthe Internet or a local area network coupled to other system computersand servers. The network computing device 800 may include one or moreantennas 807 for sending and receiving electromagnetic radiation thatmay be connected to a wireless communication link. The network computingdevice 800 may include additional access ports, such as USB, Firewire,Thunderbolt, and the like for coupling to peripherals, external memory,or other devices.

FIG. 9 shows a component block diagram of an example UE 900. In variousimplementations, the UE 900 may be similar to the wireless devices 120,120 a-120 e, 200 and include an apparatus 402 as shown in FIGS. 1-4.With reference to FIGS. 1-9, the UE 900 may include a first SOC 202 (forexample a SOC-CPU) coupled to a second SOC 204 (for example a 5G capableSOC). The first and second SOCs 202, 204 may be coupled to internalmemory 906, 916, a display 912, and to a speaker 914. Additionally, theUE 900 may include an antenna 904 for sending and receivingelectromagnetic radiation that may be connected to a wireless data linkor cellular telephone transceiver 908 coupled to one or more processingsystems in the first or second SOCs 202, 204. UE 900 typically alsoincludes menu selection buttons or rocker switches 920 for receivinguser inputs.

A UE 900 also includes a sound encoding/decoding (CODEC) circuit 910,which digitizes sound received from a microphone into data packetssuitable for wireless transmission and decodes received sound datapackets to generate analog signals that are provided to the speaker togenerate sound. Also, one or more of the processing systems in the firstand second SOCs 202, 204, wireless transceiver 908 and CODEC 910 mayinclude a digital signal processing system (DSP) circuit (not shownseparately).

The processing systems of the wireless network 900 and the UE 900 may beany programmable microprocessor, microcomputer or multiple processorchip or chips that can be configured by software instructions(applications) to perform a variety of functions, including thefunctions of some implementations described below. In some mobiledevices, multiple processors may be provided, such as one processorwithin an SOC 204 dedicated to wireless communication functions and oneprocessor within an SOC 202 dedicated to running other applications.Typically, software applications may be stored in the memory 906, 916before they are accessed and loaded into the processing system. Theprocessing systems may include internal memory sufficient to store theapplication software instructions.

Implementation examples are described in the following numbered clauses:

1. A method and an apparatus, a UE, and a non-transitory medium storinginstructions implementing the method for wireless communication by a UEin an NG-RAN, including:

receiving, at the UE, a system information block (SIB) one (SIB1) from acell of the NG-RAN;

determining, by the UE, whether the cell supports non-public networks(NPNs) based on the received SIB1;

determining, by the UE, whether an NPN-identifier (NPN-ID) in thereceived SIB1 matches an NPN-ID associated with a stored SIB in responseto determining that the cell supports NPNs based on the received SIB1;and

validating, by the UE, the stored SIB based at least in part on thereceived SIB1 in response to determining that the NPN-ID in the receivedSIB1 and the NPN-ID associated with the stored SIB match.

2. The method, apparatus, UE and non-transitory medium of clause 1,further including:

determining, by the UE, whether the cell supports NPNs based on thereceived SIB1 includes determining, by the UE, whether the cell supportsonly NPNs based on the received SIB; and

determining, by the UE, whether a NPN-identifier (NPN-ID) in thereceived SIB1 matches an NPN-ID associated with a stored SIB in responseto determining that the cell supports NPNs based on the received SIB1includes determining, by the UE, whether an NPN-ID in the received SIB1matches an NPN-ID associated with a stored SIB in response todetermining that the cell supports only NPNs based on the received SIB1.

3. The method, apparatus, UE and non-transitory medium of any of clauses1 or 2, further including indicating, by the UE, that the stored SIB isinvalid in response to determining that the NPN-ID in the received SIB1and the NPN-ID associated with the stored SIB do not match.4. The method, apparatus, UE and non-transitory medium of any of clauses1-3, where the NPN-ID is a standalone NPN (SNPN)-identifier (SNPN-ID).5. The method, apparatus, UE and non-transitory medium of clauses 4,where the SNPN-ID includes a network identifier (NID) and optionally apublic land mobile network (PLMN)-identifier (PLMN-ID).6. The method, apparatus, UE and non-transitory medium any of clauses1-3, where the NPN-ID is a combination of a public land mobile network(PLMN)-identifier (PLMN-ID) and a closed access group (CAG)-identifier(CAG-ID).7. The method, apparatus, UE and non-transitory medium of any of clauses1-6, where only a first NPN-ID in the received SIB and only a firstNPN-ID associated with the stored SIB are used to determine whether theNPN-ID in the received SIB1 matches the NPN-ID associated with thestored SIB.8. The method, apparatus, UE and non-transitory medium of any of clauses1-7, further including:

determining, by the UE, whether an NPN-identifier (NPN-ID) in thereceived SIB1 indicates that the cell is associated with a standaloneNPN (SNPN) and a network identifier of the SNPN is locally managed.

9. The method, apparatus, UE and non-transitory medium of clause 8,where the NPN-ID in the received SIB1 that indicates that the cell isassociated with the SNPN is a first NPN in the received SIB1.

10. The method, apparatus, UE and non-transitory medium of any ofclauses 8 or 9, further including:

preventing, by the UE, storage of the received SIB1 in response todetermining that the NPN-ID in the received SIB1 indicates that the cellis associated with a standalone SNPN and a network identifier of theSNPN is locally managed.

11. The method, apparatus, UE and non-transitory medium of any ofclauses 8 or 9, further including:

indicating, by the UE, any stored SIB is invalid in response todetermining that the NPN-ID in the received SIB1 indicates that the cellis associated with a standalone SNPN and a network identifier of theSNPN is locally managed.

12. The method, apparatus, UE and non-transitory medium of any ofclauses 8-11, where the network identifier of the SNPN being locallymanaged is indicated at least in part by one or more bits of the networkidentifier of the SNPN.

13. The method, apparatus, UE and non-transitory medium of any ofclauses 1-12, where the SIB1 is received on a downlink-shared channel(DL-SCH).

14. The method, apparatus, UE and non-transitory medium of any ofclauses 1-13, where the cell is a serving cell.

15. The method, apparatus, UE and non-transitory medium of any ofclauses 1-14, where the received SIB1 indicates that the cell supportsonly NPNs by one or more of:

an information element “cellreservedforotheruse” in the SIB1 set to trueand at least one standalone NPN (SNPN)-identifier (SNPN-ID) or a closedaccess group (CAG)-identifier (CAG-ID) indicated in the SIB1;

an indication in the SIB1 indicates that the cell only provides accessto NPNs; and

only one PLMN-ID is included in the information element“PLMN-IdentityInfoList” in the SIB1 and the PLMN-ID is a valueassociated with indicating NPN support.

Various implementations illustrated and described are provided merely asexamples to illustrate various features of the claims. However, featuresshown and described with respect to any given implementation are notnecessarily limited to the associated implementation and may be used orcombined with other implementations that are shown and described.Further, the claims are not intended to be limited by any one exampleimplementation. For example, one or more of the operations of themethods 500, 600, and 700 may be substituted for or combined with one ormore operations of the methods 500, 600, and 700.

As used in this application, the terms “component,” “module,” “system,”and the like are intended to include a computer-related entity, such as,but not limited to, hardware, firmware, a combination of hardware andsoftware, software, or software in execution, which are configured toperform particular operations or functions. For example, a component maybe, but is not limited to, a process running on an apparatus (such as aprocessing system), a processing system, an object, an executable, athread of execution, a program, or a computer. By way of illustration,both an application running on a wireless device and the wireless devicemay be referred to as a component. One or more components may residewithin a process or thread of execution and a component may be localizedon one processor or core of a processing system or distributed betweentwo or more processors, cores or processing systems. In addition, thesecomponents may execute from various non-transitory computer readablemedia having various instructions or data structures stored thereon.Components may communicate by way of local or remote processes, functionor procedure calls, electronic signals, data packets, memoryread/writes, and other known network, computer, processing system, orprocess related communication methodologies.

A number of different cellular and mobile communication services andstandards are available or contemplated in the future, all of which mayimplement and benefit from the various implementations. Such servicesand standards include, such as third generation partnership project(3GPP), long term evolution (LTE) systems, third generation wirelessmobile communication technology (3G), fourth generation wireless mobilecommunication technology (4G), fifth generation wireless mobilecommunication technology (5G), global system for mobile communications(GSM), universal mobile telecommunications system (UMTS), 3GSM, generalpacket radio service (GPRS), code division multiple access (CDMA)systems (such as cdmaOne, CDMA1020™), enhanced data rates for GSMevolution (EDGE), advanced mobile phone system (AMPS), digital AMPS(IS-136/TDMA), evolution-data optimized (EV-DO), digital enhancedcordless telecommunications (DECT), Worldwide Interoperability forMicrowave Access (WiMAX), wireless local area network (WLAN), Wi-FiProtected Access I & II (WPA, WPA2), and integrated digital enhancednetwork (iDEN). Each of these technologies involves, for example, thetransmission and reception of voice, data, signaling, or contentmessages. It should be understood that any references to terminology ortechnical details related to an individual telecommunication standard ortechnology are for illustrative purposes only, and are not intended tolimit the scope of the claims to a particular communication system ortechnology unless specifically recited in the claim language.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover: a, b, c,a-b, a-c, b-c, and a-b-c.

The various illustrative logics, logical blocks, modules, circuits andalgorithm processes described in connection with the implementationsdisclosed herein may be implemented as electronic hardware, computersoftware, or combinations of both. The interchangeability of hardwareand software has been described generally, in terms of functionality,and illustrated in the various illustrative components, blocks, modules,circuits and processes described above. Whether such functionality isimplemented in hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

The hardware and data processing apparatus (which may include aprocessing system) used to implement the various illustrative logics,logical blocks, modules and circuits described in connection with theaspects disclosed herein may be implemented or performed with a generalpurpose single- or multi-chip processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor may be a microprocessor, or any conventionalprocessor, controller, microcontroller, or state machine. The apparatusalso may be implemented as a combination of computing devices, such as acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. In some implementations,particular processes and methods may be performed by circuitry that isspecific to a given function.

In one or more aspects, the functions described may be implemented inhardware, digital electronic circuitry, computer software, firmware,including the structures disclosed in this specification and theirstructural equivalents thereof, or in any combination thereof.Implementations of the subject matter described in this specificationalso can be implemented as one or more computer programs, i.e., one ormore modules of computer program instructions, encoded on anon-transitory processor-readable storage media for execution by, or tocontrol the operation of, data processing apparatus.

If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. The processes of a method or algorithmdisclosed herein may be implemented in a processor-executable softwaremodule which may reside on a computer-readable medium. Computer-readablemedia includes both computer storage media and communication mediaincluding any medium that can be enabled to transfer a computer programfrom one place to another. A storage media may be any availablenon-transitory storage media that may be accessed by a computer. By wayof example, and not limitation, such computer-readable media may includeRAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic diskstorage or other magnetic storage devices, or any other medium that maybe used to store desired program code in the form of instructions ordata structures and that may be accessed by a computer. Also, anyconnection can be properly termed a computer-readable medium. Disk anddisc, as used herein, includes compact disc (CD), laser disc, opticaldisc, digital versatile disc (DVD), floppy disk, and Blu-ray disc wheredisks usually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of computer-readable media. Additionally, theoperations of a method or algorithm may reside as one or any combinationor set of codes and instructions on a machine readable medium andcomputer-readable medium, which may be incorporated into a computerprogram product.

In one or more aspects, the functions described may be implemented by anapparatus (such as a processing system), which may be coupled to amemory. The memory may be a non-transitory computer-readable storagemedium that stores processor-executable instructions. The memory maystore an operating system, user application software, or otherexecutable instructions. The memory also may store application data,such as an array data structure. The apparatus (such as a processingsystem) may read and write information to and from the memory. Thememory also may store instructions associated with one or more protocolstacks. A protocol stack generally includes computer executableinstructions to enable communication using a radio access protocol orcommunication protocol.

Various modifications to the implementations described in thisdisclosure may be readily apparent to those skilled in the art, and thegeneric principles defined herein may be applied to otherimplementations without departing from the scope of this disclosure.Thus, the claims are not intended to be limited to the implementationsshown herein, but are to be accorded the widest scope consistent withthis disclosure, the principles and the novel features disclosed herein.

Certain features that are described in this specification in the contextof separate implementations also can be implemented in combination in asingle implementation. Conversely, various features that are describedin the context of a single implementation also can be implemented inmultiple implementations separately or in any suitable subcombination.Moreover, although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. Further, the drawings may schematically depict one more exampleprocess in the form of a flow diagram. However, other operations thatare not depicted can be incorporated in the example processes that areschematically illustrated. For example, one or more additionaloperations can be performed before, after, simultaneously, or betweenany of the illustrated operations. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system components in the implementations describedabove should not be understood as requiring such separation in allimplementations, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products.Additionally, other implementations are within the scope of thefollowing claims. In some cases, the actions recited in the claims canbe performed in a different order and still achieve desirable results.

What is claimed is:
 1. A method for wireless communication performed by an apparatus of a user equipment (UE) in a next generation (NG) radio access network (RAN) (NG-RAN), comprising: receiving, at the UE, a system information block (SIB) one (SIB1) from a cell of the NG-RAN; determining, by the UE, whether the cell supports non-public networks (NPNs) based on the received SIB1; determining, by the UE, whether an NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports NPNs based on the received SIB1; determining, by the UE, whether the NPN-identifier (NPN-ID) in the received SIB1 indicates that the cell is associated with a standalone NPN (SNPN) and a network identifier of the SNPN is locally managed; preventing, by the UE, storage of the received SIB1 in response to determining that the NPN-ID in the received SIB1 indicates that the cell is associated with the SNPN and the network identifier of the SNPN is locally managed; and validating, by the UE, the stored SIB based at least in part on the received SIB1 in response to determining that the NPN-ID in the received SIB1 and the NPN-ID associated with the stored SIB match.
 2. The method of claim 1, further comprising: determining, by the UE, whether the cell supports NPNs based on the received SIB1 comprises determining, by the UE, whether the cell supports only NPNs based on the received SIB1; and determining, by the UE, whether a NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports NPNs based on the received SIB1 comprises determining, by the UE, whether an NPN-ID in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports only NPNs based on the received SIB1.
 3. The method of claim 1, further comprising: indicating, by the UE, that the stored SIB is invalid in response to determining that the NPN-ID in the received SIB1 and the NPN-ID associated with the stored SIB do not match.
 4. The method of claim 1, wherein the NPN-ID is a combination of a public land mobile network (PLMN)-identifier (PLMN-ID) and a closed access group (CAG)-identifier (CAG-ID).
 5. The method of claim 1, wherein only a first NPN-ID in the received SIB and only a first NPN-ID associated with the stored SIB are used to determine whether the NPN-ID in the received SIB1 matches the NPN-ID associated with the stored SIB.
 6. The method of claim 1, wherein the NPN-ID in the received SIB1 that indicates that the cell is associated with the SNPN is a first NPN in the received SIB1.
 7. The method of claim 1, further comprising: indicating, by the UE, any stored SIB is invalid in response to determining that the NPN-ID in the received SIB1 indicates that the cell is associated with a standalone SNPN and a network identifier of the SNPN is locally managed.
 8. The method of claim 1, wherein the network identifier of the SNPN being locally managed is indicated at least in part by one or more bits of the network identifier of the SNPN.
 9. The method of claim 1, wherein the SIB1 is received on a downlink-shared channel (DL-SCH).
 10. The method of claim 1, wherein the cell is a serving cell.
 11. The method of claim 1, wherein the received SIB1 indicates that the cell supports only NPNs by one or more of: an information element “cellreservedforotheruse” in the SIB1 set to true and at least one standalone NPN (SNPN)-identifier (SNPN-ID) or a closed access group (CAG)-identifier (CAG-ID) indicated in the SIB1; an indication in the SIB1 indicates that the cell only provides access to NPNs; and only one a public land mobile network (PLMN)-identifier (PLMN-ID) is included in the information element “PLMN-IdentityInfoList” in the SIB1 and the PLMN-ID is a value associated with indicating NPN support.
 12. An apparatus of a user equipment (UE), comprising: a first interface configured to receive a system information block (SIB) one (SIB1) from a cell of a next generation (NG) radio access network (RAN) (NG-RAN); and a processing system coupled to the first interface and configured to: determine whether the cell supports non-public networks (NPNs) based on the received SIB1; determine whether an NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports NPNs based on the received SIB1; determine whether the NPN-identifier (NPN-ID) in the received SIB1 indicates that the cell is associated with a standalone NPN (SNPN) and a network identifier of the SNPN is locally managed; prevent storage of the received SIB1 in response to determining that the NPN-ID in the received SIB1 indicates that the cell is associated with the SNPN and the network identifier of the SNPN is locally managed; and validate the stored SIB based at least in part on the received SIB1 in response to determining that the NPN-ID in the received SIB1 and the NPN-ID associated with the stored SIB match.
 13. The apparatus of claim 12, wherein the processing system is further configured to: determine whether the cell supports NPNs based on the received SIB1 by determining whether the cell supports only NPNs based on the received SIB1; and determine whether a NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports NPNs based on the received SIB1 by determining whether an NPN-ID in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports only NPNs based on the received SIB1.
 14. The apparatus of claim 12, wherein the processing system is further configured to: indicate that the stored SIB is invalid in response to determining that the NPN-ID in the received SIB1 and the NPN-ID associated with the stored SIB do not match.
 15. The apparatus of claim 12, wherein the processing system is configured such that the NPN-ID is a combination of a public land mobile network (PLMN)-identifier (PLMN-ID) and a closed access group (CAG)-identifier (CAG-ID).
 16. The apparatus of claim 12, wherein the processing system is configured such that only a first NPN-ID in the received SIB and only a first NPN-ID associated with the stored SIB are used to determine whether the NPN-ID in the received SIB1 matches the NPN-ID associated with the stored SIB.
 17. The apparatus of claim 12, wherein the processing system is configured such that the NPN-ID in the received SIB1 that indicates that the cell is associated with the SNPN is a first NPN in the received SIB1.
 18. The apparatus of claim 12, wherein the processing system is further configured to: indicate any stored SIB is invalid in response to determining that the NPN-ID in the received SIB1 indicates that the cell is associated with a standalone SNPN and a network identifier of the SNPN is locally managed.
 19. The apparatus of claim 12, wherein the first interface is configured such that the SIB1 is received on a downlink-shared channel (DL-SCH).
 20. The apparatus of claim 12, wherein the received SIB1 indicates that the cell supports only NPNs by one or more of: an information element “cellreservedforotheruse” in the SIB1 set to true and at least one standalone NPN (SNPN)-identifier (SNPN-ID) or a closed access group (CAG)-identifier (CAG-ID) indicated in the SIB1; an indication in the SIB1 indicates that the cell only provides access to NPNs; and only one a public land mobile network (PLMN)-identifier (PLMN-ID) is included in the information element “PLMN-IdentityInfoList” in the SIB1 and the PLMN-ID is a value associated with indicating NPN support.
 21. A non-transitory processor-readable medium having stored thereon processor-executable instructions configured to cause a user equipment (UE) processing system to perform operations comprising: receiving a system information block (SIB) one (SIB1) from a cell of a next generation (NG) radio access network (RAN) (NG-RAN); and determining whether the cell supports non-public networks (NPNs) based on the received SIB1; determining whether an NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports NPNs based on the received SIB1; determining whether the NPN-identifier (NPN-ID) in the received SIB1 indicates that the cell is associated with a standalone NPN (SNPN) and a network identifier of the SNPN is locally managed; preventing storage of the received SIB1 in response to determining that the NPN-ID in the received SIB1 indicates that the cell is associated with the SNPN and the network identifier of the SNPN is locally managed; and validating the stored SIB based at least in part on the received SIB1 in response to determining that the NPN-ID in the received SIB1 and the NPN-ID associated with the stored SIB match.
 22. A user equipment (UE), comprising: means for receiving a system information block (SIB) one (SIB1) from a cell of a next generation (NG) radio access network (RAN) (NG-RAN); means for determining whether the cell supports non-public networks (NPNs) based on the received SIB1; means for determining whether an NPN-identifier (NPN-ID) in the received SIB1 matches an NPN-ID associated with a stored SIB in response to determining that the cell supports NPNs based on the received SIB1; means for determining whether the NPN-identifier (NPN-ID) in the received SIB1 indicates that the cell is associated with a standalone NPN (SNPN) and a network identifier of the SNPN is locally managed; means for preventing storage of the received SIB1 in response to determining that the NPN-ID in the received SIB1 indicates that the cell is associated with the SNPN and the network identifier of the SNPN is locally managed; and means for validating the stored SIB based at least in part on the received SIB1 in response to determining that the NPN-ID in the received SIB1 and the NPN-ID associated with the stored SIB match. 